Application state backup and restoration across multiple devices

ABSTRACT

Technology for a method for backing up and restoring application state across multiple devices is disclosed herein. The method includes running an instance of a computer application at a first electronic device, determining a backup event that occurs in the first electronic device, wherein the backup event suggests a backup of application state data and the application state data represent an application state of the computer application at the backup event, and transmitting the application state data of the computer application to a remote storage service, in response to the backup event. A second electronic device can retrieve the application state data from the remote storage service and restore the application state.

PRIORITY CLAIM

This application claims to the benefit of U.S. Provisional PatentApplication No. 61/708,794, entitled “CLOUD COMPUTING INTEGRATEDOPERATING SYSTEM”, which was filed on Oct. 2, 2012, which isincorporated by reference herein in its entirety.

This application is also a continuation-in-part of U.S. patentapplication Ser. No. 13/772,163, entitled “APPLICATION STATESYNCHRONIZATION ACROSS MULTIPLE DEVICES”, which was filed on Feb. 20,2013, which is incorporated by reference herein in its entirety.

FIELD OF THE INVENTION

At least one embodiment of the present invention pertains to cloudcomputing, and more particularly, to automatic backup and restoration ofapplication states across multiple devices using cloud storage.

BACKGROUND

Application state data are data used to record the running status of acomputer application. One example of application state data is a gamesave for a game application. A game save is a piece of digitally storedinformation about the progress of a user operating the game application.The game save can be reloaded later, so that the user can continue wherehe stopped. The user instructs the game application to generate a gamesave (i.e. save the game) to prevent the loss of progress in the game,especially when he is interrupted or ending a game session.

Sharing and backing up game saves among users have been common for manyyears. Originally by swapping memory cards with game saves, users couldhelp each other to unlock features in a game application. With thegrowing popularity of the Internet, users start to upload their gamesaves from their devices to Internet servers. By downloading a game savefrom an Internet server, a user can continue the progress of the game onthe device on which he played the game or another device such as acomputer, game console, or smart phone. However, to achieve the goal ofcontinuing the progress on another device, the user needs todeliberately instruct the device to save the game progress (i.e. gamesave) and to upload the game save to a server or a memory card. Then theuser needs to download the game from the server or the memory card tothe other device, and then instructs the other device to load the gamesave. The whole process is tedious and requires many user interventions.Furthermore, the process only works for game applications that arespecifically designed with game saving functionalities.

SUMMARY

Techniques introduced here provide an automatic mechanism for backing upand restoring application state across multiple devices. In accordancewith the techniques introduced here, a method includes running aninstance of a computer application at a first electronic device, anddetermining a backup event that occurs in the first electronic device.The backup event suggests a backup of application state data and theapplication state data represent an application state of the computerapplication at the backup event. The method further includestransmitting the application state data of the computer application to aremote storage service, in response to the backup event. Anotherelectronic device can retrieve the application state data of thecomputer application from the remote storage service, and restore thecomputer application to the application state using the applicationstate data.

The backup proceeds automatically on the background of the operatingsystem of the device and is transparent to the user as well as theapplication. The user can restore the application state of theapplication running on the same device or on another device at where thestate of the application has been backed up. The application statebackup and restore can be achieved at the operating system level of thedevices. There is no special treatment or design needed for the computerapplication itself. Any computer application capable of running on suchan operating system can take advantage of the application state backupand restore functionality.

Other aspects of the technology introduced here will be apparent fromthe accompanying figures and from the detailed description whichfollows.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other objects, features and characteristics of the presentinvention will become more apparent to those skilled in the art from astudy of the following detailed description in conjunction with theappended claims and drawings, all of which form a part of thisspecification. In the drawings:

FIG. 1 illustrates an example system for application statesynchronization between electronic devices.

FIG. 2 illustrates an example of an application states synchronizationprocess across multiple electronic devices.

FIG. 3 illustrates an example operating system of an electronic device.

FIG. 4 illustrates an example of an application state data of a computerapplication collected by an operating system.

FIG. 5 illustrates an example of an application state synchronizationprocess based on a user defined synchronization scheme.

FIG. 6 illustrates an example of an application state backup andrestoration process.

FIG. 7 is a high-level block diagram showing an example of thearchitecture of a computer server, which may represent any computerrunning the database management system described herein.

DETAILED DESCRIPTION

References in this specification to “an embodiment,” “one embodiment,”or the like, mean that the particular feature, structure, orcharacteristic being described is included in at least one embodiment ofthe present invention. Occurrences of such phrases in this specificationdo not all necessarily refer to the same embodiment, however.

A method of application state synchronization across devices isdescribed herein. For example, a user plays a game on his smart phone,and stops playing and turns off the screen of his smart phone. The stateof the game application is synchronized between his smart phone andother electronic devices via a cloud system. He can pick up his tabletcomputer and continue to play the game from where he left off. Thesynchronization is not necessarily directly triggered by a userintervention. For instance, the synchronization can be automaticallytriggered when the screen of the smart phone is turned off, or the usercloses the game on his smart phone. The synchronization proceedsautomatically on the background and is transparent to the user.Furthermore, the cloud system can analyze various information, includingdevice profile, user profile and user history, to determine state ofwhich application is to be synchronized and which device the state issynchronized to.

FIG. 1 illustrates an example system for application statesynchronization between electronic devices. The system includes a cloudstorage service 110 configured to store state data for applications. Inone embodiment, the cloud storage service 110 can be a storage clusterhaving computer nodes interconnected with each other by a network. Thestorage cluster can communicate with other electronic devices via theInternet. The cloud storage service 110 contains storage nodes 112. Eachof the storage nodes 112 contains one or more processors 114 and storagedevices 116. The storage devices can include optical disk storage, RAM,ROM, EEPROM, flash memory, phase change memory, magnetic cassettes,magnetic tapes, magnetic disk storage or any other computer storagemedium which can be used to store the desired information.

A cloud synchronization interface 120 can also be included to receivedata to be stored in the cloud storage service. The cloudsynchronization interface 120 can include network communication hardwareand network connection logic to receive the information from electronicdevices. The network can be a local area network (LAN), wide areanetwork (WAN) or the Internet. The cloud synchronization interface 120may include a queuing mechanism to organize the received synchronizationdata to be stored in the cloud storage service 110. The cloudsynchronization interface 120 can communicate with the cloud storageservice 110 to send requests to the cloud storage service 110 forstoring application state data and retrieving data.

An electronic device 130 includes an operating system 132 to manage thehardware resources of the electronic device 130 and provide services forrunning computer applications 134. The computer application 134 storedin the electronic device 130 require the operating system 132 toproperly run on the device 130. The electronic device 130 can backupapplication states of the computer applications 134 to the cloud storageservice 110. The electronic device 130 includes at least one localstorage device 138 to store the computer applications, application data,and user data. The electronic device 130 can synchronize the applicationstate data with the cloud storage service 110 via the cloudsynchronization interface 120. The electronic device 130 or 140 can be adesktop computer, a laptop computer, a tablet computer, an automobilecomputer, a game console, a smart phone, a personal digital assistant,or other electronic devices capable of running computer applications, ascontemplated by a person having ordinary skill in the art.

The computer applications 134 stored in the electronic device 130 caninclude applications for general productivity and information retrieval,including email, calendar, contacts, and stock market and weatherinformation. The computer applications 134 can also include applicationsin other categories, such as mobile games, factory automation, GPS andlocation-based services, banking, order-tracking, ticket purchases orany other categories as contemplated by a person having ordinary skillin the art.

The operating system 132 of the electronic device 130 includes a statesynchronization module 136 to backup application state information fromthe local storage. The state synchronization module 136 can operate tokeep the application state data from the electronic device 130 insynchronization with the cloud storage service 110 and other devices.

Similarly, another electronic device 140 can also synchronize theapplication state with the cloud storage service 110. The electronicdevices 130 and 140 can synchronize the application states between eachother via the cloud storage service 110. For instance, the electronicdevice 130 can synchronize the application state of a computerapplication to the cloud storage service 110. The cloud storage service110 communicates with the electronic device 140 to know that theelectronic device 140 also contain this computer application and theapplication state of this computer application is not updated on theelectronic device 140. In turn, the cloud storage service 110 sends theapplication state data to the electronic device 140. Thus, theapplication state of this computer application is synchronized betweenthe electronic devices 130 and 140.

In one embodiment, the synchronization for backups from the electronicdevices 130 and 140 to the cloud storage service 110 may take place on aconfigurable periodic basis, such as an hour or a day. In other words,the synchronization is scheduled to take place on a periodic basis. Thescheduled synchronization can also check for updates that can be sentfrom the cloud storage service 110 to the electronic devices 130 and140.

Another type of synchronization can be a triggered when an event occurson the electronic device 130 or 140, and then the state synchronizationmodule can initialize the application state data synchronization withthe cloud storage service 110. The triggered synchronization does notneed the intervention from the user. For instance, a user turns off thescreen of the electronic device 130. The screen turning off event cantrigger an application state data synchronization with the cloud storageservice 110 as well as other electronic devices. However, the user doesnot need to specifically instruct the device to synchronize; the userdoes not even need to realize that the synchronization occurs.

In one embodiment, the backup event can be any of the following events:the screen of the electronic device being turned off, the instance ofthe computer application being closed, the instance of the computerapplication being paused, the instance of the computer applicationhaving been run continuously for a preconfigured period of time, theinstance of the computer application being switched by anotherapplication, the instance of the computer application being switchedfrom the foreground to a background of the operating system, a batterylevel of the electronic device being below a preconfigured value, theelectronic device turning off, the electronic device switching tostandby mode, a clock of the electronic device reaching a preconfiguredtime of day, and the electronic device being in a preconfigured location

In one embodiment, the synchronization can be a delta synchronizationwhere the electronic device 130 or 140 detects a change (i.e. delta) ofapplication state data and only the changed data or difference aresynchronized to the cloud storage device 110.

Any electronic device running an operating system having the statesynchronization module can initialize the application statesynchronization. In addition, the cloud storage service 110 can alsoinitialize the application state synchronization. In one embodiment, thecloud storage service 110 may analyze the electronic devices todetermine which device is to be synchronized and state data of whichapplication are to be synchronized.

FIG. 2 illustrates an example of an application states synchronizationprocess across multiple electronic devices. At step 205, a cloud storagesystem identifies a plurality of electronic devices capable ofsynchronizing application state data with the cloud storage system. Theelectronic devices may be capable of communicating with the cloudstorage system via a network, such as the Internet, a WiFi Network, or acellular phone network. At step 210, one of the identified electronicdevices runs an application.

At step 215, a backup event is determined to occur at the electronicdevice. The operating system of the electronic device automaticallydetermines the backup event, without the intervention from the user. Theuser does not specifically instruct the backup event. The user does noteven need to realize the backup event. There is no need for a syncbutton, a sync gesture, a sync menu item, or a sync command. In otherwords, the operating system of the device makes the determination of abackup event. For instance, the operating system may recognize an eventof the screen being turned off as a backup event. The operating systemmay also recognize an event of a running application being closed orbeing switched by another application as a backup event. The operatingsystem may further recognize an event of a system standby as a backupevent. The operating system of the device can determine other types ofbackup events, as contemplated by a person having ordinary skill in theart.

Once the operating detects a backup event, the operating system of theelectronic device uploads the application state data of the computerapplication onto the cloud storage system at step 220. The operatingsystem of the device may decide to immediately start uploading theapplication state data after the backup event, or start the upload acertain amount of time after the backup event. For instance, if theelectronic device detects that there is another electronic device of thesame user in a very close proximity, the operating system of the devicemay decide to start the upload immediately because of a high possibilitythat the user will start using the other device soon. In anotherembodiment, the electronic device may decide to start the upload at acertain time of day or at certain location. For instance, the electronicdevice may decide to start the upload at midnight 12 AM and at theuser's home (determined by GPS location or WiFi location), so that theupload of the application state data does not intervene with normaloperation of the device.

In one embodiment, the developer of the computer application does notneed to specifically write any implementation for uploading theapplication state data. For example, there are no API calls embedded inthe computer application for the application state data. The statesynchronization module of the operating system is responsible formonitoring, collecting and uploading the application state data. In someembodiments, the state synchronization module compares the currentapplication state on the device and the application state already storedin the cloud storage service. If the current application state is newerthan the application state stored in the cloud storage service, thestate synchronization module determines a difference (i.e. delta)between the current application state data and the application statedata stored in the cloud storage service. In this way, the statesynchronization module only needs to upload the difference to the cloudstorage service. The cloud storage service is responsible forincorporating the difference into the application state data alreadystored.

At step 225, the cloud storage system performs an analysis on the deviceprofile, user profile and user history, to determine which device thestate is synchronized to. For instance, in one embodiment, the cloudstorage system determines the devices that the same user is using (e.g.the devices which have established the user's user account). In anotherembodiment, the analysis is based on usage pattern. For example, thecloud storage service can determine to synchronize the application stateto devices that the user has been frequently used during a specific timeperiod, e.g. a week. Or the cloud storage service can determine tosynchronize the application state to devices on which the user has beenrunning that computer application. In yet another embodiment, theanalysis is based on a proximity algorithm. For example, the cloudstorage service can determine to synchronize the application state todevices that are physically close to the device in step 210. Theproximity may be determined by GPS locations, WiFi network locations,cellular networking locations or the combination thereof. In stillanother embodiment, the analysis is based on the types of applicationsinstalled on the devices. For example, the cloud storage service candetermine to synchronize the application state to devices that haveinstances of that application installed, or devices that have similarapplications installed. Furthermore, the analysis can be determined by acombination of the above techniques, as well as any other device or userinformation as contemplated by a person having ordinary skill in theart.

The same types of analysis disclosed in the previous paragraph are usedin determining the priority of synchronization. For instance, if thereare application state data for multiple applications in the cloudstorage service to be synchronized. The cloud storage service maydetermine to synchronize the state data for one application because theuser has been frequently using that application during a recent timeperiod, e.g. a week. In one embodiment, the cloud storage servicedecides a priority list including a reference to the application statedata for the computer application, wherein the priority list regulatesthe order of transmitting the application state data for the computerapplication and data for other applications based on the analyzing ofthe user profile and the hardware profiles of electronic devices.

In some embodiments, the analysis is performed after the cloud storagesystem receives application state data from a device. In some otherembodiments, the analysis can be performed before the cloud storagesystem receives any application state data or before the backup eventoccurs.

At step 230, the cloud storage system sends the application state datato one or more devices that are identified by the analysis. Theidentified devices receive the application state data. Therefore, theinstances of the application running on the devices are synchronizedwith the most up-to-date state. A user can run an instance of theapplication on any of these devices and the instance of the applicationresumes from the most up-to-date state. In one embodiment, the cloudstorage system further sends an instruction to each of the identifieddevices to run an instance of the computer application by resuming theapplication state at the backup event at step 235.

In one embodiment, the application state data of a computer applicationmay include application memory data, application local storage data,hardware configuration data, and user account configuration data. Thestate synchronization module of the operating system is capable ofcollecting these data and uploading the data as included in theapplication state data to the cloud storage service. Based on theapplication state data, an operating system of another electronic devicecan recreate the same environment and status of the application on theother electronic device.

In some embodiments, the electronic devices are capable of synchronizingapplication state data between each other via a network, such as a WiFinetwork, Bluetooth network, or a cellular phone network. Each of theelectronic devices contains a network component configured to directlysynchronize the application state data with another electronic device.

FIG. 3 illustrates an example operating system of an electronic device,according to one embodiment. The operating system 300 includes a kernel304. The kernel 304 provides interfaces to hardware of the electronicdevice for the computer applications running on top of the kernel 304,and supervises and controls the computer applications. The kernel 304isolates the computer applications from the hardware. The kernel 304 mayinclude one or more intervening sources that can affect execution of acomputer application. In one embodiment, the kernel 304 includes anetwork I/O module 306, a file I/O module 308, multi-threading module310, user input 314, system interrupts 316, and shared memory access318.

A state synchronization module 330 runs on top of the kernel 304. Thestate synchronization module 330 monitors the information from theintervening sources of the kernel 304 and records state data accordingthe information. In the example of FIG. 3, a computer application 340includes a binary executable code 342 that can run on top of theoperating system 300. The computer application 340 can further includestatic and dynamic libraries 344 that are referenced by the binaryexecutable code 342 during application running. In one embodiment, thestate synchronization module 330 runs in a user space file system (e.g.FUSE) on top of a Linux kernel. In another embodiment, the statesynchronization module 330 runs in a kernel file system.

FIG. 4 illustrates an example of an application state data of a computerapplication collected by an operating system according to oneembodiment. The application state data 400 of a computer application mayinclude application memory data 402, application local storage data 404,hardware configuration data 406, and user account configuration data408. In some other embodiments, the application state data can be all ofor any combination of some of the fields 402, 404, 406 and 408. When thecomputer application is running, the state information in memory section(i.e. the application memory data 402) allocated for the application isbeing updated by the running application. The state synchronizationmodule of the operating system monitors the application memory data 402,and uploads the data to a cloud storage service in response to thebackup event. Furthermore, the computer application can update certaindata on a local storage of the electronic device. The statesynchronization module of the operating system can include theapplication local storage data 404 into the application state data 400.In some embodiments, the electronic device includes a memory device,e.g. flash memory, as both the memory and the local storage. Therefore,the application memory data 402 and application local storage data 404can be one section of data that exists on the memory device of theelectronic device.

The application state data 400 may further include hardwareconfiguration data 406. For instance, the state synchronization modulemay record the current device sound volume level and the screenbrightness level when the application is running. These device soundvolume level and the screen brightness level are recorded as part of thehardware configuration data 405 and will be uploaded to the cloudstorage service. Therefore, after another device is synchronized withthe application state data and starts to resume running the application,the other device automatically adjusts the sound volume level and screenbrightness level as on the previous device. Moreover, the applicationstate data 400 may include user account configuration data 408. The useraccount configuration data 408 may include the user's preferences andchoices regarding the computer application and the operating systemenvironment for running the computer application. For instance, the useraccount configuration data 408 may include information about the user'slanguage preference. Assuming the computer application is a gamesupporting both English and Chinese languages for user interface in thegame, the user has selected the English language as the preferredlanguage. The state synchronization module records the user's languagepreference as a part of the user account configuration data 408. Theuser account configuration data 408 is synchronized to another devicevia the cloud storage service. When the other device starts to resumerunning the application, the application will use the English languagefor the game interface, as indicated by the user account configurationdata 408.

In some embodiments, a user can define a synchronization scheme tocontrol the way how and when the synchronization process performs. FIG.5 illustrates an example of an application state synchronization processbased on a user defined synchronization scheme. At step 505, a cloudstorage service receives an instruction of a synchronization scheme froma user. The synchronization scheme includes rules of how and when thesynchronization process performs. For example, in one embodiment, thesynchronization scheme can define a synchronization rule between twoelectronic devices, a smart phone and a tablet computer, for applicationstate of a game application. The synchronization rule specifies that oneof the electronic devices start attempting to synchronize applicationstate to the other device, as soon as the game application is closed orthe screen of the device being turned off.

Assuming the smart phone is the current device running the gameapplication, at step 510, the operating system of the smart phone checkswhether the game application is closed by the user. If the gameapplication is closed, the process continues to step 520. Otherwise, atstep 515 the operating system of the smart phone continues to checkwhether the screen of the smart phone is turned off. If the screen isturned off, the process continues to step 520. Otherwise, the processgoes back to check the status as in steps 510 and 520 in a predeterminedtime period.

At step 520, the smart phone uploads application state data of the gameapplication to the cloud storage system. The schedule of the uploadingcan depend on a type and a speed of a connection between the smart phoneand the could storage system. For instance the schedule can bedetermined so that the uploading is delayed to use a WiFi connection, toavoid the uploading using a cellular data connection (e.g. 3G or LTE).At step 525, the cloud storage system reads the synchronization schemedefined by the user. At step 530, the cloud storage system checkswhether the other device, i.e. the tablet computer, is currently beingconnected with the cloud storage system. If the tablet computer isconnected with the cloud storage system, the system sends theapplication state data to the tablet computer according to thesynchronization scheme at 535. Otherwise, the cloud storage systemcontinues to check the connection with the tablet computer on a periodicbasis.

At step 540, when the user starts to use the tablet computer, the tabletcomputer starts to run an instance of the game application by resumingthe application state recorded in the synchronized application statedata.

In some embodiments, an electronic device can automatically back up theapplication state data to a cloud storage service and restore theapplication state be retrieving the application state data from thecloud storage service. FIG. 6 illustrates an example of an applicationbackup and restore process. At step 605, an first electronic device runsan instance of a computer application. At step 610, the first electronicdevice determines a backup event that occurs in the first electronicdevice. The backup event suggests a backup of application state data andthe application state data represent an application state of thecomputer application at the backup event. The backup event can beautomatic and does not need to be instructed by a user who is operatingthe instance of the computer application.

At step 615, the first electronic device transmits the application statedata of the computer application to a remote storage service, inresponse to the backup event. The remote storage service can be a cloudcomputing service. Alternatively, the remote storage service can belongto a cloud storage service cluster. The first electronic device iscapable of transmitting the application state data to the remote storageservice via a network, which can include the Internet, a WiFi network,or a cellular phone network. In one embodiment, the first electronicdevice can immediately transmit the application state data of thecomputer application to a remote storage service in real time withoutsubstantial delay, in response to the backup event.

The application state data of the computer application can betransmitted to the remote storage service at a preconfigured time of dayor when the first electronic device is at a preconfigured location, inresponse to the backup event. Alternatively, the application state dataof the computer application can be transmitted to the remote storageservice at a schedule depending on a type and a speed of a connectionbetween the first electronic device and the remote storage service, inresponse to the backup event. The schedule can be determined so that thetransmitting is delayed to use a WiFi connection, to avoid thetransmitting using a cellular data connection. The backup can beincremental. For instance, a difference between the application statedata of the computer application and previously transmitted applicationstate data can be transmitted to a remote storage service, in responseto the backup event.

In some embodiments, the first electronic device may further determine arestore event that occurs in the electronic device, wherein the restoreevent suggests a restore of the application state of the computerapplication at the second electronic device; and instructs the remotestorage service to transmit the application state data of the computerapplication to the second electronic, in response to the restore event.

Alternatively, a second electronic device can perform the process ofrestoring the application state. At step 620, the second electronicdevice determines a restore event that occurs in a second electronicdevice. The restore event suggests a restore of the application state ofthe computer application at the second electronic device. At step 625,the second electronic device can further instruct the remote storageservice to transmit the application state data of the computerapplication to the second electronic device, in response to the restoreevent. At step 630, the second electronic device restores the computerapplication to the application state using the application state data.

FIG. 7 is a high-level block diagram showing an example of thearchitecture of a computer, which may represent any electronic device orany server within a cloud storage service as described herein. Theserver 700 includes one or more processors 710 and memory 720 coupled toan interconnect 730. The interconnect 730 shown in FIG. 7 is anabstraction that represents any one or more separate physical buses,point to point connections, or both connected by appropriate bridges,adapters, or controllers. The interconnect 730, therefore, may include,for example, a system bus, a Peripheral Component Interconnect (PCI) busor PCI-Express bus, a HyperTransport or industry standard architecture(ISA) bus, a small computer system interface (SCSI) bus, a universalserial bus (USB), IIC (I2C) bus, or an Institute of Electrical andElectronics Engineers (IEEE) standard 1394 bus, also called “Firewire”.

The processor(s) 710 is/are the central processing unit (CPU) of theserver 700 and, thus, control the overall operation of the server 700.In certain embodiments, the processor(s) 710 accomplish this byexecuting software or firmware stored in memory 720. The processor(s)710 may be, or may include, one or more programmable general-purpose orspecial-purpose microprocessors, digital signal processors (DSPs),programmable controllers, application specific integrated circuits(ASICs), programmable logic devices (PLDs), trusted platform modules(TPMs), or the like, or a combination of such devices.

The memory 720 is or includes the main memory of the server 700. Thememory 720 represents any form of random access memory (RAM), read-onlymemory (ROM), flash memory, or the like, or a combination of suchdevices. In use, the memory 720 may contain a code 770 containinginstructions according to the techniques disclosed herein.

Also connected to the processor(s) 710 through the interconnect 730 area network adapter 740 and a storage adapter 750. The network adapter 740provides the server 700 with the ability to communicate with remotedevices, over a network and may be, for example, an Ethernet adapter orFibre Channel adapter. The network adapter 740 may also provide theserver 700 with the ability to communicate with other computers. Thestorage adapter 750 allows the server 700 to access a persistentstorage, and may be, for example, a Fibre Channel adapter or SCSIadapter.

The code 770 stored in memory 720 may be implemented as software and/orfirmware to program the processor(s) 710 to carry out actions describedabove. In certain embodiments, such software or firmware may beinitially provided to the server 700 by downloading it from a remotesystem through the server 700 (e.g., via network adapter 740).

The techniques introduced herein can be implemented by, for example,programmable circuitry (e.g., one or more microprocessors) programmedwith software and/or firmware, or entirely in special-purpose hardwiredcircuitry, or in a combination of such forms. Special-purpose hardwiredcircuitry may be in the form of, for example, one or moreapplication-specific integrated circuits (ASICs), programmable logicdevices (PLDs), field-programmable gate arrays (FPGAs), etc.

Software or firmware for use in implementing the techniques introducedhere may be stored on a machine-readable storage medium and may beexecuted by one or more general-purpose or special-purpose programmablemicroprocessors. A “machine-readable storage medium”, as the term isused herein, includes any mechanism that can store information in a formaccessible by a machine (a machine may be, for example, a computer,network device, cellular phone, personal digital assistant (PDA),manufacturing tool, any device with one or more processors, etc.). Forexample, a machine-accessible storage medium includesrecordable/non-recordable media (e.g., read-only memory (ROM); randomaccess memory (RAM); magnetic disk storage media; optical storage media;flash memory devices; etc.), etc.

The term “logic”, as used herein, can include, for example, programmablecircuitry programmed with specific software and/or firmware,special-purpose hardwired circuitry, or a combination thereof.

In addition to the above mentioned examples, various other modificationsand alterations of the invention may be made without departing from theinvention. Accordingly, the above disclosure is not to be considered aslimiting and the appended claims are to be interpreted as encompassingthe true spirit and the entire scope of the invention.

What is claimed is:
 1. A computer-implemented method comprising: runningan instance of a computer application at a first electronic device;determining a backup event that occurs in the first electronic device,wherein the backup event suggests a backup of application state data andthe application state data represents an application state of thecomputer application at the backup event; transmitting the applicationstate data of the computer application to a remote storage service, inresponse to the backup event; determining a restore event that occurs ina second electronic device, wherein the restore event suggests a restoreof the application state of the computer application at the secondelectronic device; and instructing the remote storage service totransmit the application state data of the computer application to thesecond electronic device, in response to the restore event, so that thesecond electronic device restores the computer application to theapplication state using the application state data, wherein the step oftransmitting includes transmitting the application state data of thecomputer application to a remote storage service at a schedule dependingon a type and a speed of a connection between the first electronicdevice and the remote storage service, in response to the backup event.2. The computer-implemented method of claim 1, wherein the firstelectronic device executes the transmitting the application state dataat a background of an operating system of the first electronic devicewithout user intervention.
 3. The computer-implemented method of claim1, further comprising determining a restore event that occurs in thefirst electronic device, wherein the restore event suggests a restore ofthe application state of the computer application at the firstelectronic device; and retrieving the application state data of thecomputer application from the remote storage service, in response to therestore event, so that the first electronic device can restore thecomputer application to the application state using the applicationstate data.
 4. The computer-implemented method of claim 1, furthercomprising: receiving a confirmation that the computer application hasbeen restored to the application state using the application state data.5. The computer-implemented method of claim 1, wherein the remotestorage service is a cloud computing service or the remote storageservice belongs to a cloud storage service cluster.
 6. Thecomputer-implemented method of claim 1, wherein the backup event is notinstructed by a user who is operating the instance of the computerapplication.
 7. The computer-implemented method of claim 1, wherein thesync event is an event of the screen of the first electronic devicebeing turned off.
 8. The computer-implemented method of claim 1, whereinthe first electronic device is capable of transmitting the applicationstate data to the remote storage service via a network.
 9. Thecomputer-implemented method of claim 7, wherein the network includes theInternet, a WiFi network, or a cellular phone network.
 10. Thecomputer-implemented method of claim 1, wherein the step of transmittingincludes: immediately transmitting the application state data of thecomputer application to a remote storage service, in response to thebackup event.
 11. The computer-implemented method of claim 1, whereinthe step of transmitting includes: transmitting the application statedata of the computer application to a remote storage service at apreconfigured time of day or when the first electronic device is at apreconfigured location, in response to the backup event.
 12. Thecomputer-implemented method of claim 1, wherein the backup event is anevent from events including: the instance of the computer applicationbeing closed, the instance of the computer application being paused, theinstance of the computer application has been continuously running for apreconfigured period of time, the instance of the computer applicationbeing switched by another application, a battery level of the firstelectronic device being below a preconfigured value, the firstelectronic device turning off, the first electronic device switching tostandby mode, a clock of the first electronic device reaching apreconfigured time of day, or the first electronic device being at apreconfigured location.
 13. The computer-implemented method of claim 11,wherein the schedule is determined so that the transmitting is delayedto use a WiFi connection, to avoid the transmitting using a cellulardata connection.
 14. The computer-implemented method of claim 1, whereinthe step of transmitting includes: transmitting a difference between theapplication state data of the computer application and previouslytransmitted application state data to a remote storage service, inresponse to the backup event.
 15. An electronic device comprising: aprocessor; a memory storing instructions which, when executed by theprocessor, cause the electronic device to perform a process including:running an instance of a computer application at the electronic device,determining a backup event that occurs in the electronic device, whereinthe backup event suggests a backup of application state data and theapplication state data represents an application state of the computerapplication at the backup event, and transmitting the application statedata of the computer application to a storage server, in response to thebackup event, wherein the application state data is used by anotherelectronic device to restore the computer application to the applicationstate on the other electronic device, wherein transmitting theapplication state data includes transmitting the application state dataof the computer application to a remote storage service at a scheduledepending on a type and a speed of a connection between the firstelectronic device and the remote storage service, in response to thebackup event.
 16. The electronic device of claim 15, wherein the processfurther includes: determining a restore event that occurs in theelectronic device, wherein the restore event suggests a restore of theapplication state of the computer application at the electronic device;and retrieving application state data of the computer application fromthe storage server, in response to the restore event.
 17. The electronicdevice of claim 16, wherein the process further includes: restoring thecomputer application to the application state at the electronic deviceusing the application state data.
 18. The electronic device of claim 15,wherein the application state data includes application memory data,application local storage data, hardware configuration data, or useraccount configuration data.
 19. The electronic device of claim 15,wherein the computer application is a game application and theapplication state data includes game save data for the game application.20. A computer-implemented method comprising: receiving applicationstate data from a first electronic device, wherein the application statedata represents an application state at a backup event of a computerapplication running at the first electronic device; determining a useridentity for a user who runs the computer application at the firstelectronic device; receiving a notice of a restore event including theuser identity; identifying the application state data associated withthe user identity; and transmitting the application state data to asecond electronic device, wherein the application state data is utilizedby the computer application to resume the application state at therestore event at the second electronic device, wherein the step oftransmitting includes transmitting the application state data of thecomputer application to a remote storage service at a schedule dependingon a type and a speed of a connection between the first electronicdevice and the remote storage service, in response to the backup event.21. A cloud based server comprising: a processor; a memory storinginstructions which, when executed by the processor, cause the cloudbased server to perform a process including: receiving a notice of abackup event from a first electronic device, wherein the backup eventsuggests a backup of application state data and the application statedata represent an application state of a computer application running atthe first electronic device at the backup event; receiving a notice of arestore event from a second electronic device, wherein the restore eventsuggests a restore of the application state of the computer applicationat the second electronic device; receiving the application state data ofthe computer application from the first electronic device in response tothe backup event; and transmitting the application state data to thesecond electronic device in response to the notice of the restore eventfrom the second electronic device, wherein a transmission of theapplication state data from the first electronic device, in response tothe backup event, to the cloud based server, is at a schedule dependingon a type and a speed of a connection between the first electronicdevice and the cloud based server.
 22. The cloud based server of claim21, wherein the cloud based server receives the application state datafrom the first electronic device in such a manner that the firstelectronic device processes the application state data at a backgroundof an operating system of the first electronic device without userintervention.
 23. The cloud based server of claim 21, wherein theprocess further includes: determining a priority list including areference to the application state data, wherein the priority listregulates the order of transmitting the application state data for thecomputer application and data for other applications based on ananalysis of a user profile and a hardware profile of at least the firstelectronic device.
 24. An electronic device comprising: a processor; anon-transitory computer-readable medium storing instructions which, whenexecuted by the processor, cause the electronic device to performoperations including: executing a computer application; generatingapplication state data that represent an application state of thecomputer application at a background of an operating system of theelectronic device without user intervention; sending out the applicationstate data to a cloud service, the sending of the application state datato the cloud service being triggered by a backup event, wherein thesending of the application state data to the cloud service is at aschedule depending on a type and a speed of a connection between theelectronic device and the cloud service; and instructing anotherelectronic device to retrieve the application state data from the cloudservice to restore the application state of the computer application onthe other electronic device.
 25. The electronic device of claim 24,wherein the application state data can be generated at any moment duringthe execution of the computer application, or continuously generatedduring the execution of the computer application.
 26. The electronicdevice of claim 24, wherein the operating system of the electronicdevice sends the application state data according to a synchronizationscheme defined by a user on how and when to transmit.
 27. The electronicdevice of claim 24, wherein the operating system includes a state moduleresponsible for monitoring, collecting and transmitting the applicationstate data.